Systems and methods for processing digital experience information

ABSTRACT

In one implementation, systems and methods are provided for processing digital experience information. A computer-implemented system for processing digital experience information may comprise a central data location. The central data location may comprise a connector that may be configured to receive information belonging to a category from an information source; an event backbone that may be configured to route the information received by the connector based on the category; a translator that may be configured to transform the received information into a common data model; and a database that may be configured to store the received information. The event backbone may be further configured to send information to the connector from the event backbone and the database based on one or more criteria.

PRIORITY

The present application claims priority to Provisional U.S. PatentApplication Ser. No. 62/983,535, filed Feb. 28, 2020, the disclosure ofwhich is incorporated herein by reference.

The present application incorporates by reference Provisional U.S.Patent Application Ser. No. 62/983,529, filed Feb. 28, 2020, andProvisional U.S. Application Ser. No. 62/983,581, filed Feb. 29, 2020.The patent applications cited herein are incorporated by reference intheir entireties, except for any definitions, subject matter disclaimersor disavowals, and except to the extent that the incorporated materialis inconsistent with the express disclosure herein, in which case thelanguage in this disclosure controls.

TECHNICAL FIELD

The present disclosure relates generally to computer-implemented systemsand methods for processing digital experience information. Morespecifically, and without limitation, this disclosure relates tocomputer-implemented systems and methods for translating digitalexperience information into a common data model. The systems and methodsdisclosed herein may be used in various applications, such as businesssystems and systems comprising various sources of digital experienceinformation and/or systems of record.

BACKGROUND

In digital application systems, it is often desirable to collectinformation in a central accessible data location. A central datalocation simplifies storage and retrieval of information, allowingdisparate systems to capture and share data. It also simplifiesintegration of new features, allowing data collected from an existingsystem to be used by a new system for example, reducing the time neededto release new features and applications. Existing systems and methodsfor processing digital experience information, however, suffer from anumber of drawbacks, including the inability to provide real-timeinformation. In addition, existing systems and methods are unable toperform deep data exploration, since handling large data with existingsystems of record is cost prohibitive. Furthermore, existing systems andmethods are cumbersome to use in that they require complex integrationand intricate data schema designs to operate.

In view of the foregoing, the inventors have identified that there is aneed for improved systems and methods for processing digital experienceinformation.

SUMMARY

In view of the foregoing, embodiments of the present disclosure providecomputer-implemented systems and methods for processing digitalexperience information. The description below provides exemplary aspectsof some computer-implemented systems and methods for processing digitalexperience information in accordance with some exemplary embodiments.Aspects may be combined with one or more suitable described aspects orother undescribed aspects. Aspects of one exemplary system or method maybe combined with aspects of other exemplary systems, methods, or both.

An exemplary computer-implemented system for processing digitalexperience information may comprise a system of record configured toreceive, from a publisher, a transactional event. The transactionalevent may comprise a transactional event data. The system may comprise acentral data location communicatively connected to the system of record.The central data location may comprise an ingestion connector configuredto receive the transactional event data from the system of record. Thecentral data location may comprise a translator configured to transformthe transactional event data from the ingestion connector into a commondata scheme. The central data location may comprise an event backbonecommunicatively connected to the translator. The event backbone maycomprise a topic. The topic may comprise the transactional event data inthe common data scheme received from the translator. The central datalocation may include an event store communicatively connected to theevent backbone. The event store may be configured to receive a topicfrom the event backbone. The event store may be configured to store thetopic in a storage system. The central data location may include astreaming processor configured to stream the transactional event data toa subscriber.

The common data scheme may be configured to allow integration betweentransactional events.

The storage system may be configured to allow an out-of-order query tomodify query cost.

The streaming processor may be configured to stream the transactionalevent in real-time.

The streaming processor may be configured to receive the transactionalevent data from the event backbone. The event backbone may be configuredto receive the transactional event data from the event store.

The streaming processor may be configured to receive the transactionaldata from the event store. The event backbone may be communicativelyconnected to the ingestion connector.

The event backbone may comprise an ingestion topic comprising thetransactional event data before it is transformed, by the translator,into the common data scheme. The common data scheme may be BIAN (BankingIndustry Architecture Network). The topic may be a BIAN topic. Thetranslator may be configured to transform the transactional event datafrom the ingestion connector into a BIAN-compliant data scheme.

The event backbone may comprise a purpose-built topic comprising aportion of the transactional event data that is not compliant with thecommon data scheme.

The central data location may comprise a business rules engineconfigured to supply business rules to the streaming processor. Thestreaming processor may be further configured convert the transactionalevent data into the common data scheme using the business rules.

The streaming processor may comprise a business rule, and the streamingprocessor may be further configured to convert the transactional eventdata into the common data scheme using the business rule.

The event backbone may further comprise a sink connector communicativelyconnected to the event store. The sink connector may be configured totransform the transactional event data from a topic into a query datascheme for storage in the event store. The sink connector may beconfigured to write the topic to the event store.

The event backbone may further comprise an access logs topiccommunicatively coupled to a log management system. The access logstopic may be configured to record access to the event backbone.

The event store may be further configured to permanently store thetransactional event. The event store may comprise a database. Thedatabase may be a RDBMS database. The database may be a NoSQL database.

An exemplary computer-implemented method for processing digitalexperience information may comprise the step of receiving atransactional event from a publisher. The transactional event maycomprise transactional event data. The method may comprise the step ofdetermining whether the transactional event data is compliant with acommon data scheme. The method may comprise the step of transforming thetransactional event data into common data scheme compliant data. Themethod may comprise the step of storing the common data scheme data inan event store. The method may comprise the step of exposing the commondata scheme compliant data to a subscriber in real-time.

The method may comprise the step of receiving a request from thesubscriber to expose the common data scheme compliant data. The requestmay allow the subscriber to query the common data scheme compliant dataon an ad-hoc basis.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise an ingestion connector. The ingestionconnector may be configured to receive, from a system of record, atransactional event comprising transactional event data. The ingestionconnector may be configured to collect the transactional event data fromthe transactional event. The ingestion connector may be configured toplace the transactional event data onto a data scheme topic. Theingestion connector may comprise a change data capture configured todetermine and track data changes. The central data location may includean event backbone. The event backbone may be communicatively connectedto the ingestion connector. The event backbone may comprise a commondata scheme topic comprising one or a plurality of transactional events.The common data scheme topic may be formed from the data scheme topic.The central data location may comprise an event store communicativelyconnected to the event backbone. The event store may be configured toreceive the common data scheme topic from the event backbone. The eventstore may be configured to store the common data scheme topic in astorage system. The central data location may comprise a streamingprocessor configured to stream the transactional event data to asubscriber.

The common data scheme topic may comprise transactional event data thatthe change data capture determined is changed.

The ingestion connector may further comprise a message-orientedmiddleware component communicatively connected to the change datacapture.

The ingestion connector may further comprise a connecting logiccommunicatively connected to the change data capture. The connectinglogic may be configured to connect the ingestion connector to the eventbackbone.

The system of record may be configured to be aware of the eventbackbone, allowing the ingestion connector to receive the transactionalevent in real-time.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise an ingestion connector. The ingestionconnector may be configured to receive, from a system of record, a batchfile. The batch file may comprise transactional event data. Theingestion connector may comprise a batch file processor. The batch fileprocessor may be configured to place the transactional event data onto adata scheme topic. The central data location may comprise an eventbackbone. The event backbone may comprise a common data scheme topic.The common data scheme topic may comprise one or a plurality oftransactional events. The common data scheme topic may be formed fromthe data scheme topic. The central data location may comprise an eventstore configured to store the common data scheme topic. The central datalocation may comprise a streaming processor configured to stream, to asubscriber, a data scheme message.

The system of record may be configured to be aware of the eventbackbone, allowing the ingestion connector to receive the transactionalevent in real-time.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise a publisher configured to publish, to asystem of record, a transactional event comprising transactional eventdata. The publisher may be configured to collect the transactional eventdata from the transactional event. The publisher may be configured toplace the transactional event data onto a data scheme topic. The datascheme topic may comprise a data scheme message. The central datalocation may comprise an event backbone. The event backbone may comprisea common data scheme topic. The common data scheme topic may compriseone or a plurality of transactional events. The common data scheme topicmay be formed from the data scheme message. The central data locationmay comprise an event store configured to store the common data schemetopic. The central data location may comprise a streaming processorconfigured to stream, to a subscriber, the data scheme message.

The central data location may further comprise a business rules engineconfigured to supply business rules to the publisher. The publisher maybe further configured to convert the transactional event data into acommon data scheme using the business rules. The publisher may comprisea business rule. The publisher may be further configured to convert thetransactional event data into a common data scheme using the businessrule.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise an ingestion connector. The ingestionconnector may be configured to receive in real-time, from a system ofrecord, a transactional event comprising transactional event data. Theingestion connector may be configured to collect the transactional eventdata from the transactional event. The ingestion connector may beconfigured to place the transactional event data onto an ingestion topicin an ingestion topic message. The central data location may comprise atranslator configured to transform the ingestion topic message into acommon data scheme message. The central data location may comprise anevent backbone. The event backbone may comprise a topic comprising oneor a plurality of transactional events. The topic may be formed from thecommon data scheme message. The central data location may comprise anevent store configured to store the topic. The central data location maycomprise a streaming processor configured to stream, to a subscriber,the common data scheme message.

The translator may be further configured to enrich the ingestion topicmessage with external data by calling an API. The external data may beBIAN compliant data. The external data may be geographic data. The APImay be communicatively coupled to a library. The API may be configuredto convert the common data scheme message into a BIAN compliant datascheme.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise an ingestion connector. The ingestionconnector may be configured to receive in real-time, from a system ofrecord, a transactional event comprising transactional event data. Theingestion connector may be further configured to collect thetransactional event data from the transactional event. The ingestionconnector may be further configured to place the transactional eventdata into a common data scheme message. The ingestion connector may befurther configured to place the common data scheme message containingthe transactional event data onto a topic. The topic may comprise one ora plurality of transactional events. The central data location maycomprise a sink connector configured to transform the topic into apurpose-built topic. The sink connector may be configured to write thetopic to an event store. The central data location may comprise an eventstore configured to store the topic. The central data location maycomprise a streaming processor. The streaming processor may beconfigured to transform the common data scheme message into a querymessage. The streaming processor may be configured to stream the querymessage to a subscriber.

The event store may be a JDBC compliant data store. The sink connectormay be a JDBC sink connector.

The streaming processor may be further configured to enrich the commondata scheme message with external data by calling an API. The externaldata may be BIAN compliant data. The external data may be geographicdata. The API may be communicatively coupled to a library. The API maybe configured to convert the common data scheme message into a BIANcompliant data scheme.

The central data location may further comprise a business rules engine.The business rules engine may be configured to supply business rules tothe streaming processor. The streaming processor may be configured totransform the common data scheme message into the query message usingthe business rules.

The streaming processor may further comprise a business rule. Thestreaming processor may be configured to transform the common datascheme message into the query message using the business rule.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise an ingestion connector. The ingestionconnector may be configured to receive in real-time, from a system ofrecord, a transactional event comprising transactional event data. Theingestion connector may be further configured to collect thetransactional event data from the transactional event. The ingestionconnector may be configured to place the transactional event data into acommon data scheme message. The ingestion connector may be configured toplace the common data scheme message containing the transactional eventdata onto a topic. The topic may comprise one or a plurality oftransactional events. The central data location may comprise an eventstore configured to store the topic. The central data location maycomprise a streaming processor. The streaming processor may beconfigured to write the topic to the event store. The streamingprocessor may be configured to read the topic from the event store. Thestreaming processor may be configured to expose the topic to asubscriber.

The streaming processor may comprise a cache. The streaming processormay be further configured to read the topic from the cache.

The streaming processor may be further configured to enrich the commondata scheme message, with external data, by calling an API. The externaldata may be BIAN compliant data. The external data may be geographicdata. The API may be communicatively coupled to a library. The API maybe configured to convert the common data scheme message into a BIANcompliant data scheme. The central data location may further comprise abusiness rules engine configured to supply business rules to thestreaming processor. The streaming processor may be further configuredto convert the common data scheme message from the topic into a querymessage using the business rules. The streaming processor may beconfigured to place the query message onto a topic.

The streaming processor may comprise a business rule. The streamingprocessor may be further configured to convert the common data schememessage from the topic into a query message using the business rule. Thestreaming processor may be further configured to place the query messageonto a topic.

The streaming processor may be further configured to indicate a currentstate of the subscriber. The current state may comprise requesting thetopic. The current state may comprise having received the topic.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise an ingestion connector. The ingestionconnector may be configured to receive in real-time, from a system ofrecord, a transactional event comprising transactional event data. Theingestion connector may be configured to collect the transactional eventdata from the transactional event. The ingestion connector may beconfigured to place the transactional event data, in a common datascheme message, onto a topic comprising one or a plurality oftransactional events. The central data location may comprise an eventstore. The event store may be configured to store the topic. The eventstore may be able to expose the topic to a subscriber.

The event store may be configured to expose the topic using an APIinterface. The API interface may be configured to use a MICRONframework. The event store may comprise an event store schema. The APIinterface may comprise an API schema. The event store schema may followthe API schema. The event store schema may be identical to the APIschema.

The subscriber may comprise an internal cache.

The subscriber may comprise an external cache.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise an ingestion connector. The ingestionconnector may be configured to receive in real-time, from a system ofrecord, a transactional event. The transactional event may comprisetransactional event data. The ingestion connector may be configured tocollect the transactional event data from the transactional event. Theingestion connector may be configured to place the transactional eventdata, in a common data scheme message, onto a topic. The topic maycomprise one or a plurality of transactional events. The topic may beconfigured to expose the common data scheme message to a subscriber.

The topic may be configured to expose the common data scheme messageusing an API. The subscriber may comprise an internal cache. Thesubscriber may comprise an external cache. The API may be configured toread the topic. The topic may be a Kafka topic.

An exemplary computer-implemented system for processing digitalexperience information may comprise a central data location. The centraldata location may comprise an ingestion connector. The ingestionconnector may be configured to receive in real-time, from a system ofrecord, a transactional event. The transactional event may comprisetransactional event data. The ingestion connector may be furtherconfigured to collect the transactional event data from thetransactional event. The ingestion connector may be configured to placethe transactional event data onto an ingestion topic in an ingestiontopic message. The central data location may comprise a translatorconfigured to transform the ingestion topic message into a common datascheme message. The central data location may comprise an eventbackbone. The event backbone may comprise a common data scheme topic.The common data scheme topic may comprise one or a plurality oftransactional events. The common data scheme topic may be formed fromthe common data scheme message. The event backbone may comprise anaccess logs topic communicatively coupled to a log management system.The access logs topic may be configured to record access to the eventbackbone. The event backbone may comprise a sink connector. The sinkconnector may be configured to transform the topic into a purpose-builttopic. The sink connector may be configured to write the topic to anevent store. The central data location may comprise an event storeconfigured to store the topic. The central data location may comprise astreaming processor configured to stream, to a subscriber, the commondata scheme message.

The ingestion topic may comprise an ingestion topic schema defined usinga schema registry. The common data scheme topic may comprise a commondata scheme topic schema defined using the schema registry. Thepurpose-built topic may comprise a purpose-built topic schema definedusing the schema registry. The access log topic may comprise an accesslog topic schema using the schema registry.

The schema registry may follow a serialization and deserializationstandard.

The serialization and deserialization standard may be Apache Avro.

An exemplary computer-implemented central data location may comprise aningestion connector. The ingestion connector may be configured toreceive in real-time, from a system of record, a transactional eventcomprising transactional event data. The ingestion connector may beconfigured to collect the transactional event data from thetransactional event. The ingestion connector may be configured todetermine whether the transactional event data is common data schemecompliant. If the transactional event data is common data schemecompliant, the ingestion connector may be configured to place thetransactional event data onto a common data scheme topic in a commondata scheme topic message. The common data scheme topic may comprise oneor a plurality of transactional events. If the transactional event datais not common data scheme compliant, the ingestion connector may beconfigured to place the transactional event data onto an ingestion topicin an ingestion topic message. The ingestion connector may be configuredto transform the ingestion topic message into a common data schememessage. The ingestion connector may be configured to place the commondata scheme message onto a common data scheme topic. The central datalocation may comprise an event backbone. The event backbone may comprisethe ingestion topic. The event backbone may comprise the common datascheme topic. The central data location may comprise an event store. Theevent store may be configured to store the common data scheme topic. Thecentral data location may comprise a streaming processor. The streamingprocessor may be configured to stream, to a subscriber, the common datascheme message.

The event backbone may further comprise an access logs topic. The accesslogs topic may be communicatively coupled to a log management system.The log management system may be configured to record access to theevent backbone.

The event backbone may further comprise a sink connector configured totransform the common data scheme topic into a purpose-built topic. Thesink connector may be configured to write the topic to an event store.The purpose-built topic may comprise data that is not common data schemecompliant. The event store may be further configured to store the topic.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which comprise a part of this specification,illustrate several embodiments and, together with the description, serveto explain the principles and features of the disclosed embodiments. Inthe drawings:

FIG. 1 is a pictorial representation of an exemplary channel applicationin accordance with some embodiments.

FIG. 2 is a schematic representation of an exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments.

FIG. 3 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments.

FIG. 4 is a flowchart of an exemplary computer-implemented method forprocessing digital experience information in accordance with someembodiments.

FIG. 5 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using a passiveingestion connector.

FIG. 6 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using a passiveingestion connector.

FIG. 7 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using an activeingestion connector.

FIG. 8 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using a translator.

FIG. 9 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using a sink connector.

FIG. 10 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using a streamingapplication.

FIG. 11 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using an API interfacefor reading from an event store.

FIG. 12 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using an API interfacefor reading from an event backbone.

FIG. 13 is a schematic representation of another exemplarycomputer-implemented system for processing digital experienceinformation in accordance with some embodiments using a schema registry.

DETAILED DESCRIPTION Systems and Methods with a Central Data Locationand Common Data Scheme

Reference will now be made in detail to exemplary embodiments, discussedwith regards to the accompanying drawings. In some instances, the samereference numbers will be used throughout the drawings and the followingdescription to refer to the same or like parts. Unless otherwisedefined, technical and/or scientific terms have the meaning commonlyunderstood by one of ordinary skill in the art. The disclosedembodiments are described in sufficient detail to enable those skilledin the art to practice the disclosed embodiments. It is to be understoodthat other embodiments may be utilized and that changes may be madewithout departing from the scope of the disclosed embodiments. Forexample, unless otherwise indicated, method steps disclosed in thefigures can be rearranged, combined, or divided without departing fromthe envisioned embodiments. Similarly, additional steps may be added orsteps may be removed without departing from the envisioned embodiments.Thus, the materials, methods, and examples are illustrative only and arenot intended to be necessarily limiting. All figures discussed hereinare to be interpreted inclusively, meaning that aspects of one or morefigures may be combined with aspects of any one or more other figures.

FIG. 1 depicts a channel application 100 that allows a user to viewinformation about banking in accordance with some embodiments. In someembodiments, channel application 100 may include a graphical userinterface (GUI) configured to enable and allow a user to viewinformation about banking as described herein. In some embodiments,channel application 100 may be embodied as software stored innontransitory computer-readable medium that when executed by a processorcauses operations, functions, and results described herein to berealized A user may use a channel application 100 on a computer, mobiledevice (e.g., cellular phone, smart phone, tablet, personal digitalassistant, smart appliance, kiosk, etc.), or other electronic device toreview or interact with banking information. The channel application 100may include micro-application 102, that tracks one or more depositaccounts. The channel application 100 may include a micro-application104, that creates a summary of one or more credit card accounts.Organizing the channel application 100 into the micro-applications 102and 104 allows digital application developers to work independently fromone another on separate features and functions. The micro-applications102 and 104 also allow developers to avoid rewriting code for the sametasks when developing new applications.

A micro-application can be configured to perform one or more discretefunctions (e.g., by using logic embodied in computer-readable and/orexecutable code). The micro-application can comprise a front-endconfigured to receive input from a user (e.g., through buttons, or thelike) and/or provide information to the user (e.g., through a display,or the like). For example, a micro-application may contain a front-endcreated using Angular for receiving user input in the form ofmouse-clicks on a browser. The micro-application can comprise an outerinterface (e.g., an application programming interface (API), or thelike) for receiving and sending information from and to the informationprocessing system using the connector (e.g., using an externalapplication programming interface (API), or the like). For example, amicro-application may contain an outer interface created usingBootstrap, and the processing system may contain a correspondingexternal application interface for communicating with the outerinterface. In some embodiments, the front-end and the outer interfacemay be deployed as a separate container in a container application(e.g., OpenShift Container Platform, or the like). The micro-applicationcan further comprise an event manager configured to send and receiveevent information to and from the information processing system, as wellas a state manager configured to send and receive state information toand from the information processing system. For example, the eventmanager may publish information regarding business events such asfinancial transactions by a customer to the event backbone through asystem of recording using a first external application programminginterface (API), and the state manager may receive information regardingthe customer's present account balance from the event backbone using asecond external application programming interface (API). In this manner,the read and write functionality between micro-applications and theprocessing system may be scaled differently.

When an event or a transaction occurs, a respective micro-applicationusing data from such events or transactions will need to update with newinformation so as to provide the user with the correct information. Forexample, if the user makes a deposit into their checking account, theuser may want to see the new balance and the amount deposited into theaccount. As another example, the user may want to see the amount theyhave charged to their credit card in another event. When an eventoccurs, a set of data may be generated in a variety of schemes. Forexample, in the event of a credit card transaction, the event maygenerate data that includes the credit card number and the dollar amountof the transaction. In a bank transfer, the transaction may generatedata, including a bank account number. Different transactions anddifferent protocols generate data that is organized in different formatsor data schemas.

Different data schemes can cause a number of issues, including addingcomplexity to communications between micro-applications, requiringspecific code to be written for two or more micro-applications to shareinformation. This adds increased cost and time to developers. Someembodiments disclosed herein reduce or eliminate the complexity ofprogramming different micro-applications to handle data of differentdata schemes. The embodiments disclosed herein allow channel application100 and micro-applications 102 and 104 to access data in a common datascheme such that the data is easily used as input, output, or both.Specifically and by way of example, some embodiments involve creating abook of reference in a common data scheme such that themicro-applications may more readily access and write data-without eachapplication needed to process the data itself. These embodiments providenumerous advantages to developers of applications such as the channelapplication 100 and the micro-applications 102 and 104, providingefficiency to developers and to the systems that process the data.Additionally, the benefits may be realized by a user. For example, thesystems may more readily allow a user to view banking information in thechannel application 100 and the micro-applications 102 and 104 in realtime, since the data is more easily and efficiently accessed by theapplications 100 through 104.

FIG. 2 depicts an exemplary computer-implemented system 200 forprocessing digital experience information, in accordance with someembodiments. System 200 may comprise one or more connectors (e.g.,connector 210) that may be configured to send and receive informationbelonging to a category to and from one or more sources of information;one or more event backbones (e.g., event backbone 220) that may beconfigured to route the received information using the category; one ormore translators (e.g., translator 230) that may be configured totransform received information into a common data model; and one or moredatabases (e.g., database 240) for storing the received information. Insome embodiments, system 200 may comprise a streaming component (notshown) that may be configured to read information in system 200 on anad-hoc or real-time basis, and which may be configured to furtherprocess the information. In various embodiments, system 200 may furthercomprise a dashboard (not shown) that may be configured to manageinformation in system 200 (e.g., by interacting with backbone 220 ordatabase 240).

Connector 210 may be configured to send and receive informationbelonging to a category to and from one or more sources of information.In some embodiments, connector 210 may comprise an interface. Forexample, connector 210 may comprise an external application programminginterface (API) that a digital application (e.g., a micro-application)may use to send and receive information to and from connector 210. Invarious embodiments, connector 210 may comprise an ingestion connectorconfigured to send and receive information to and from one or moresystems of record. For example, connector 210 may comprise amessage-oriented middleware component (e.g., MQ, or the like) andconnecting logic created using a stream-processing software platform(e.g., ActiveMQ, RabbitMQ, Amazon Kinesis, Apache Spark, Akka, ApacheStorm, Apache Flink, Redis, ZeroMQ, or the like). As an additionalexample, connector 210 may further comprise logic configured todetermine and track data that has changed (e.g., change data capture(CDC), or the like). As a further example, connector 210 may compriselogic configured to receive information periodically. For example,connector 210 may comprise a batch file processor.

Event backbone 220 may be configured to route the received informationusing a category to which the information belongs. For example, eventbackbone 220 may categorize received information into topics belongingto three general categories: ingestion topics for information in aschema other than the common data model, such as a schema belonging tothe system of record (e.g., a table, file, or the like); common datamodel topics for information in a schema compliant with the common datamodel; and purpose-built topics for information in a schema that doesnot fit into the common data model due to gaps in the common data model(e.g., due to the information having data not recognized by the commondata model). Event backbone 220 may be further configured to routeinformation based on the category. For example, event backbone 220 mayroute information belonging to the ingestion topics to translator 230 tobe transformed into the common data model, and information belonging tothe common data model topics or the purpose-built topics to database 240for storage. Event backbone 220 may be further configured to sendinformation to connector 210. For example, event backbone 220 may sendinformation to connector 210 on an ad-hoc basis, or as a result of anevent. In some embodiments, event backbone 220 may be configured toreceive information that has been modified by an external application.For example, event backbone 220 send information to a streamingcomponent for further processing (e.g., based on user actions receivedthrough, for example, an application programming interface (API), or thelike). The streaming component may then send the modified information toevent backbone 220.

Translator 230 may be configured to transform received information intoa common data model. In some embodiments, translator 230 may beconfigured to transform all information belonging to a category. Forexample, translator 230 may indicate to event backbone 220 that itwishes to receive information belonging to the ingestion topic category,commonly referred to as “subscribing.” In this manner, all informationnot complying with the common data scheme may be transformed withoutsharing it to other components of the system.

FIG. 3 depicts an exemplary computer-implemented system 300 forprocessing digital experience information in accordance with someembodiments. The computer-implemented system 300 may create a book ofreference that includes data for all types of events, such as banking orcredit transactions. Such a book of reference may be a central datalocation and may be used, for example, by applications, includingmicro-applications, to read and write data.

The computer-implemented system 300 may comprise a system of record 302configured to receive, from a publisher 304, a transactional event 306.The transactional event 306 may comprise transactional event data. Thesystem 300 may comprise a central data location 308 communicativelyconnected to the system of record 302. The central data location 308 maycomprise an ingestion connector 310 configured to receive thetransactional event data from the system of record 302. The central datalocation 308 may comprise a translator 312 configured to transform thetransactional event data from the ingestion connector 310 into a commondata scheme. The common data scheme may be configured to allowintegration between transactional events. For example, a transactionalevent of one type (e.g., a credit card payment) could be configured inthe same data scheme as a transactional event of another type (e.g., abanking transfer), so that the transactional events can each be accessedby an application. The common data scheme may be BIAN (Banking IndustryArchitecture Network scheme).

The central data location 308 may comprise an event backbone 314communicatively connected to the translator 312. The event backbone maycomprise an ingestion topic 316. The event backbone 314 may comprise acommon data scheme topic 318. The common data scheme topic 318 maycomprise the transactional event data in the common data scheme receivedfrom the translator 312. When the ingestion connector 310 receives atransactional event 306 from the system of record 302, it may determinewhether the transactional event 306 is in the common data scheme.

If the transactional event data in the transactional event 306 is not inthe common data scheme, the ingestion connector 310 can determine topass the transactional event 306 to the ingestion topic 316 in aningestion topic message. The translator 312 may then read from theingestion topic 316, translate the transactional event data in thetransactional event 306 to the common data scheme and write to thecommon data scheme topic 318. The event backbone 314, therefore, maycomprise the ingestion topic 316 comprising the transactional event databefore it is transformed, by the translator 312, into the common datascheme.

If the transactional event data of the transactional event 306 isalready in the common data scheme, the ingestion connector 310 may thenwrite to the common data scheme topic 318 without translation by thetranslator 312.

The central data location 308 may include an event store 320communicatively connected to the event backbone 314. The event store 320may be configured to receive the ingestion topic 316 or common datascheme topic 318 from the event backbone 314. The event store 320 may beconfigured to store the topic in a storage system 322. The storagesystem 322 may be configured to allow an out-of-order query to modifyquery cost.

The central data location 308 may include a streaming processor 324configured to stream the transactional event data to a subscriber. Thestreaming processor 324 may be configured to stream the transactionalevent in real-time. The streaming processor 324 may be configured toreceive the transactional event data 306 from the event backbone. Theevent backbone 314 may be configured to receive the transactional eventdata from the event store 320. The streaming processor 324 may beconfigured to receive the transactional data from the event store 320.The event backbone 314 may be communicatively connected to the ingestionconnector 310. The event backbone 314 may comprise a purpose-built topic326 comprising a portion of the transactional event data that is notcompliant with the common data scheme.

The central data location may comprise a business rules engine 328configured to supply business rules to the streaming processor 324. Thebusiness rules engine 328 may externalize business rules fromapplication code. The streaming processor 324 may be further configuredto convert the transactional event data into the common data schemeusing the business rules. The streaming processor 324 may comprise abusiness rule, and the streaming processor 324 may be further configuredto convert the transactional event data into the common data schemeusing the business rule.

The event backbone 314 may further comprise a sink connector 330communicatively connected to the event store 320. The sink connector 330may be configured to transform the transactional event data from thetopic 316, 318, or 325 into a query data scheme for storage in the eventstore 320. The sink connector 330 may be configured to write the topics316, 318, or 325 to the event store 320. The sink connector 330 may beconfigured to transform the common data scheme topic 318 into apurpose-built topic. The topic may be a BIAN topic. The translator 312may be configured to transform the transactional event data from theingestion connector 310 into a BIAN-compliant data scheme.

The event backbone 314 may further comprise an access logs topic 332communicatively coupled to a log management system 334. The access logstopic 332 may be configured to record access to the event backbone 314.

The event store 320 may be further configured to permanently store thetransactional event 306. The event store 320 may comprise a database336. The database 336 may be a RDBMS database. The database 336 may be aNoSQL database.

FIG. 4 depicts an exemplary computer-implemented method 400 forprocessing digital experience information in accordance with someembodiments. The method 400 may comprise the step 402 of receiving atransactional event from a publisher. The transactional event maycomprise transactional event data. The method may comprise the step 404of determining whether the transactional event data is compliant with acommon data scheme. The method may comprise the step 406 of transformingthe transactional event data into common data scheme compliant data. Themethod may comprise the step 408 of storing the common data scheme datain an event store. the method may comprise the step 410 of receiving arequest from the subscriber to expose the common data scheme compliantdata. The request may allow the subscriber to query the common datascheme compliant data on an ad-hoc basis. The method may comprise thestep 412 of exposing the common data scheme compliant data to asubscriber in real-time.

System with a Passive Ingestion Connector

In some exemplary systems as disclosed herein, passive ingestionconnectors can collect data in real-time and copy the data into an eventbackbone to make the data available for processing. The data may beavailable for processing, for example, by streaming applications withlittle to no changes on an existing system of record. A change datacapture as part of the passive ingestion connector may be used for sucha system. Additionally or alternatively, batch file ingestion may beused as part of a passive ingestion connector.

FIG. 5 depicts an exemplary computer-implemented system 500 forprocessing digital experience information in accordance with someembodiments. The system 500 may comprise a central data location 502.The central data location 502 may comprise an ingestion connector 504.The ingestion connector 504 may be configured to receive, from a systemof record 506, a transactional event 508 comprising transactional eventdata. The ingestion connector 504 may be configured to collect thetransactional event data from the transactional event 506. The ingestionconnector 504 may be configured to place the transactional event dataonto a data scheme topic 510. The ingestion connector 504 may comprise achange data capture 512 configured to determine and track data changes.The change data capture 512 may aid in real-time collection of data bythe ingestion connector 504 by, for example, reducing the amount of datato be passed.

The central data location may include an event backbone 514. The eventbackbone 514 may be communicatively connected to the ingestion connector504. The event backbone may comprise a common data scheme topic 516. Thecommon data scheme topic 516 may comprise one or a plurality oftransactional events. The common data scheme topic 516 may be formedfrom the data scheme topic 510. The common data scheme topic 516 maycomprise transactional event data that the change data capture 512determined is changed.

The central data location 502 may comprise an event store 518communicatively connected to the event backbone 514. The event store 518may be configured to receive the common data scheme topic 516 from theevent backbone 514. The event store 518 may be configured to store thecommon data scheme topic 516 in a storage system 519. The central datalocation 502 may comprise a streaming processor 520 configured to streamthe transactional event data to a subscriber.

The ingestion connector 504 may further comprise a message-orientedmiddleware component 522 communicatively connected to the change datacapture 512. The ingestion connector may further comprise a connectinglogic 524 communicatively connected to the change data capture 512 andthe middleware component 522. The connecting logic 524 may be configuredto connect the ingestion connector 504 to the event backbone 514.

The system of record 506 may be configured to be aware of the eventbackbone 514, allowing the ingestion connector 504 to receive thetransactional event 508 in real-time.

Batch file processor may also be used for passive ingestion. FIG. 6depicts an exemplary computer-implemented system 600 for processingdigital experience information in accordance with some embodiments. Thesystem 600 may comprise a central data location 602. The central datalocation 602 may comprise an ingestion connector 604. The ingestionconnector 604 may be configured to receive, from a system of record 606,a batch file 608.

The batch file 608 may comprise transactional event data. The ingestionconnector 604 may comprise a batch file processor 610. The batch fileprocessor 610 may be configured to place the transactional event dataonto a data scheme topic 612. The central data location 602 may comprisean event backbone 614. The event backbone 614 may comprise a common datascheme topic 616. The common data scheme topic 616 may comprise one or aplurality of transactional events. The common data scheme topic 616 maybe formed from the data scheme topic 612. The central data location 602may comprise an event store 618 configured to store the common datascheme topic 616. The central data location 602 may comprise a streamingprocessor 620 configured to stream, to a subscriber, a data schememessage. The system of record 606 may be configured to be aware of theevent backbone 614, allowing the ingestion connector 604 to receive theone or a plurality of transactional events in real-time.

System with an Active Ingestion Connector

In some exemplary systems as disclosed herein, active ingestionconnectors can enable a system of record to send data in real-time to anevent backbone. In some exemplary systems, active ingestion connectorsmay use publishers, such as APIs, to write directly to topics for activeingestion. FIG. 7 depicts an exemplary computer-implemented system 700for processing digital experience information in accordance with someembodiments. The system 700 may comprise a central data location 702.The central data location 702 may comprise a publisher 704 configured topublish, to a system of record 706, a transactional event 708 comprisingtransactional event data. The publisher 704 may be configured to collectthe transactional event data from the transactional event 708. Thepublisher 704 may be configured to place the transactional event dataonto a data scheme topic 710. The data scheme topic 710 may comprise adata scheme message. The central data location 702 may comprise an eventbackbone 712. The event backbone 712 may comprise a common data schemetopic 714. The common data scheme topic 714 may comprise one or aplurality of transactional events. The common data scheme topic 714 maybe formed from the data scheme message. The central data location 702may comprise an event store 716 configured to store the common datascheme topic 714. The central data location 702 may comprise a streamingprocessor 718 configured to stream, to a subscriber, the data schememessage.

The central data location 702 may comprise a business rules engine 720configured to supply business rules to the publisher 704. The publisher704 may be further configured to convert the transactional event datainto a common data scheme using the business rules. The publisher 704may comprise a business rule. The publisher 704 may be furtherconfigured to convert the transactional event data into a common datascheme using the business rule.

System with a Translator

Some computer implemented systems disclosed herein include translatorsoperable to transform ingestion topic messages into common data schememessages. Additionally, some computer implemented systems disclosedherein allow ingestion topics to be enriched by an API. The translatingand enriching functionality are one way some systems disclosed hereinmay create a book of reference in a common data scheme for numerousapplications, such as micro-applications. FIG. 8 depicts an exemplarycomputer-implemented system 800 for processing digital experienceinformation in accordance with some embodiments. The system 800 maycomprise a central data location 802. The central data location 802 maycomprise an ingestion connector 804. The ingestion connector 804 may beconfigured to receive in real-time, from a system of record 806, atransactional event 808 comprising transactional event data. Theingestion connector 804 may be configured to collect the transactionalevent data from the transactional event 808. The ingestion connector 804may be configured to place the transactional event data onto aningestion topic 810 in an ingestion topic message 811. The central datalocation 802 may comprise a translator 812 configured to transform theingestion topic message 811 into a common data scheme message 813. Thecentral data location 802 may comprise an event backbone 814. The eventbackbone 814 may comprise a topic 816 comprising one or a plurality oftransactional events. The topic 816 may be formed from the common datascheme message 813. The central data location 802 may comprise an eventstore 820 configured to store the topic 816. The central data location802 may comprise a streaming processor 822 configured to stream, to asubscriber, the common data scheme message 813.

The translator 812 may be configured to enrich the ingestion topicmessage 811 with external data—that is data from sources other thandirectly from the ingestion connector 804—by calling an API 824. Theexternal data may be BIAN compliant data. The external data may begeographic data. The external data may originate from applications,components of the central data location, or any other suitable origin.The API 824 may be communicatively coupled to a library 826. The library826 may supply data or executable operations for processing or producingdata. The API 824 may be configured to convert the common data schememessage 813 into a BIAN compliant data scheme.

Accordingly, as shown in FIG. 8, the translator 812 is operable toreceive an ingestion topic message 811 and translate the message 811into a common data scheme message 813. The translator 812 is alsooperable to use external data, such as the API 824 to further processthe data. Finally, the translator writes the common data scheme message813 to the topic 816 in a common data scheme. The translator 812, hasthereby transformed the ingestion topic message 811 into a common datascheme format. The underlying transactional event data contained withinthe ingestion topic message can now be stored via the event store 820 orwritten to the streaming processor 822. Now in the common data schemeformat, the one or more transactional events are now easily accessibleby other applications and by the user from the event store 820 and thestreaming processor 822.

System with a Sink Connector

Some embodiments of the present disclosure may comprise a sinkconnector. The sink connector may write events into an event store suchthat the data can be queried. Therefore, a sink connector can allow abook of reference or central data location to access stored data such ashistorical data. FIG. 9 depicts an exemplary computer-implemented system900 for processing digital experience information in accordance withsome embodiments. The system 900 may comprise a central data location902. The central data location 902 may comprise an ingestion connector904. The ingestion connector 904 may be configured to receive inreal-time, from a system of record 906, a transactional event 908comprising transactional event data. The ingestion connector 904 may befurther configured to collect the transactional event data from thetransactional event 908. The ingestion connector 904 may be furtherconfigured to place the transactional event data into a common datascheme message 910. The ingestion connector 904 may be furtherconfigured to place the common data scheme message 910 containing thetransactional event data onto a topic 912. The topic 912 may compriseone or a plurality of transactional events. The central data location902 may comprise a sink connector 914 configured to transform the topic912 into a purpose-built topic. The sink connector 914 may be configuredto map, write, or send the transactional event data of the topic 912 toan event store 916 of the central data location 902. The event store 916may be configured to store the topic 912. The central data location 902may comprise a streaming processor 918. The streaming processor 918 maybe configured to transform the common data scheme 910 message into aquery message 920. The streaming processor 918 may be configured toplace the common data scheme message onto a topic 921. The streamingprocessor 918 may be configured to stream the query message 920 to asubscriber.

The event store 916 may be a JDBC (Java Database Connectivity) compliantdata store. The sink connector 914 may be a JDBC sink connector.

The streaming processor 918 may be further configured to enrich thecommon data scheme message 910 with external data by calling an API 922.The external data may be BIAN compliant data. The external data may begeographic data. The API 922 may be communicatively coupled to a library924. The API 922 may be configured to convert the common data schememessage 910 into a BIAN compliant data scheme.

The central data location 902 may further comprise a business rulesengine 926. The business rules engine 926 may be configured to supplybusiness rules to the streaming processor 918. The streaming processor918 may be configured to transform the common data scheme message 910into the query message 920 using the business rules.

The streaming processor 918 may further comprise a business rule. Thestreaming processor 918 may be configured to transform the common datascheme message 910 into the query message 920 using the business rule.

System with a Streaming Application

In some embodiments, a streaming application may allow a view ofreal-time event streams for data sets or changing data. A streamingapplication can read a current state from an event store and makecalculations from a message, and then write a new state to the eventstore. FIG. 10 depicts an exemplary computer-implemented system 1000 forprocessing digital experience information in accordance with someembodiments. The system 1000 may comprise a central data location 1002.The central data location 1002 may comprise an ingestion connector 1004.The ingestion connector 1004 may be configured to receive in real-time,from a system of record 1006, a transactional event 1008 comprisingtransactional event data. The ingestion connector 1004 may be furtherconfigured to collect the transactional event data from thetransactional event 1008. The ingestion connector 1004 may be configuredto place the transactional event data into a common data scheme message1010. The ingestion connector 1004 may be configured to place the commondata scheme message 1010 containing the transactional event data onto atopic 1012. The topic 1012 may comprise one or a plurality oftransactional events. The central data location 1002 may comprise anevent store 1014 configured to store the topic 1012. The central datalocation 1002 may comprise a streaming processor 1016. The streamingprocessor 1016 may be configured to write the topic 1012 to the eventstore 1014. The streaming processor 1016 may be configured to read thetopic 1012 from the event store 1014. The streaming processor 1016 maybe configured to expose the topic 1012 to a subscriber 1018.

The streaming processor 1016 may comprise a cache 1017. The streamingprocessor 1016 may be configured to read the topic 1012 from the cache1017.

The streaming processor 1016 may be further configured to enrich thecommon data scheme message 1010, with external data, by calling an API1018. The API 1018 may be a subscriber to the streaming processor 1016.The external data may be BIAN compliant data. The external data may begeographic data. The API 1018 may be communicatively coupled to alibrary 1020. The API 1018 may be configured to convert the common datascheme message 1010 into a BIAN compliant data scheme. The central datalocation 1002 may further comprise a business rules engine 1022configured to supply business rules to the streaming processor 1016. Thestreaming processor 1016 may be further configured to convert the commondata scheme message 1010 from the topic 1012 into a query message 1024using the business rules. The streaming processor 1016 may be configuredto place the query message 1024 onto a topic 1026.

The streaming processor 1016 may comprise a business rule and may befurther configured to convert the common data scheme message 1010 fromthe topic 1012 into the query message 1024 using the business rule. Thestreaming processor 1016 may be further configured to place the querymessage onto the topic 1012 or a topic 1026.

The streaming processor 1016 may be further configured to indicate acurrent state of the subscriber 1018. The current state may comprise arequest state requesting the topic. The current state may comprise areceive state having received the topic.

System with an API Interface for Reading from an Event Store

In some embodiments, one or more APIs may be used to read from adatabase of an event store. FIG. 11 depicts an exemplarycomputer-implemented system 1100 for processing digital experienceinformation in accordance with some embodiments. The system 1100 maycomprise a central data location 1102. The central data location 1102may comprise an ingestion connector 1104. The ingestion connector 1104may be configured to receive in real-time, from a system of record 1106,a transactional event 1108 comprising transactional event data. Theingestion connector 1104 may be configured to collect the transactionalevent data from the transactional event 1108. The ingestion connector1104 may be configured to place the transactional event data, in acommon data scheme message 1110, onto a topic 1112 comprising one or aplurality of transactional events. The central data location 1102 maycomprise a streaming processor 1111 configured to write the topic 1112to an event store 1113. The event store 1113 may be configured to storethe topic 1112. The event store 1113 may be able to expose the topic1112 to a subscriber 1116. The subscriber 1116 may be an API that ispart of or all of an API interface 1114.

The event store 1113 may be configured to expose (i.e., enable accessto) the topic 1112 using the API interface 1114. The API interface 1114may be configured to use a MICRON framework. The event store 1113 maycomprise an event store schema. The API interface 1114 may comprise anAPI schema. The event store schema may follow the API schema. The eventstore schema may be identical to the API schema.

The API interface 1114 may comprise a cache 1118. While the cache 1118may be external, as shown in FIG. 11, the cache 1118 may alternativelybe internal to the subscriber 1116.

System with an API Interface for Reading from an Event Backbone

It may be beneficial to read directly from topics of an event backbone.Such an application may be useful, for example, when a topic contains asmall set of objects, where a state table can be rebuilt by reprocessingall events. FIG. 12 depicts an exemplary computer-implemented system1200 for processing digital experience information in accordance withsome embodiments. The system 1200 may comprise a central data location1202. The central data location 1202 may comprise an ingestion connector1204. The ingestion connector 1204 may be configured to receive inreal-time, from a system of record 1206, a transactional event 1208. Thetransactional event 1208 may comprise transactional event data. Theingestion connector 1204 may be configured to collect the transactionalevent data from the transactional event 1208. The ingestion connector1204 may be configured to place the transactional event data, in acommon data scheme message 1210, onto a topic 1212 of the event backbone1213. The topic 1212 may comprise one or a plurality of transactionalevents. The topic 1212 may be configured to expose the common datascheme message 1210 to a subscriber 1214 (e.g., an API).

The topic 1212 may be configured to expose the common data schememessage 1210 using an API, wherein the subscriber 1214 is an API. Thesubscriber 1214 may comprise a cache 1216. While shown with a cache 1216that is external to the subscriber 1214, the subscriber 1214 may have aninternal cache. The subscriber 1214 may be part of an API interface1218. The subscriber 1214 may be configured to read the topic 1212. Thetopic 1212 may be a Kafka topic.

System with a Schema Registry

It may be beneficial to use a schema registry that defines topics. FIG.13 depicts an exemplary computer-implemented system 1300 for processingdigital experience information in accordance with some embodiments. Thesystem 1300 may comprise a central data location 1302. The central datalocation 1302 may comprise an ingestion connector 1304. The ingestionconnector 1304 may be configured to receive in real-time, from a systemof record 1306, a transactional event 1308. The transactional event 1308may comprise transactional event data. The ingestion connector 1304 maybe further configured to collect the transactional event data from thetransactional event 1308. The ingestion connector 1304 may be configuredto place the transactional event data onto an ingestion topic 1310 in aningestion topic message 1312. The central data location 1302 maycomprise a translator 1313 configured to transform the ingestion topicmessage 1312 into a common data scheme message 1314. The central datalocation 1302 may comprise an event backbone 1316. The event backbone1316 may comprise a common data scheme topic 1318. The common datascheme topic 1318 may comprise one or a plurality of transactionalevents. The common data scheme topic 1318 may be formed from the commondata scheme message 1314. The event backbone 1316 may comprise an accesslogs topic 1320 communicatively coupled to a log management system 1322.The access logs topic 1320 may be configured to record access to theevent backbone 1316. The access logs topic 1320 may report the access tothe log management system 1322. The log management system 1322 may beconfigured to store log access information. The event backbone 1316 maycomprise a sink connector 1324. The sink connector 1324 may beconfigured to write one or more of topics 1310, 1318, 1320, and apurpose-built topic 1326 to an event store 1328. The event store 1328may be configured to store one or more of topics 1310, 1318, 1320, and1326. The central data location 1302 may comprise a streaming processor1330 configured to stream, to a subscriber 1332, the common data schememessage 1314.

The ingestion topic 1310 may comprise an ingestion topic schema definedusing a schema registry 1334. The common data scheme topic 1314 maycomprise a common data scheme topic schema defined using the schemaregistry 1334. The purpose-built topic 1326 may comprise a purpose-builttopic schema defined using the schema registry. The access log topic1320 may comprise an access log topic schema using the schema registry1324. The schema registry 1334 may follow a serialization anddeserialization standard. The serialization and deserialization standardmay be Apache Avro.

The present disclosure has been presented for purposes of illustration.It is not exhaustive and is not limited to precise forms or embodimentsdisclosed. Modifications and adaptations of the embodiments will beapparent from consideration of the specification and practice of thedisclosed embodiments. For example, the described implementationsinclude hardware, but systems and methods consistent with the presentdisclosure can be implemented with hardware and software. In addition,while certain components have been described as being coupled to oneanother, such components may be integrated with one another ordistributed in any suitable fashion.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations and/or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as nonexclusive.Further, the steps of the disclosed methods can be modified in anymanner, including reordering steps and/or inserting or deleting steps.

The features and advantages of the disclosure are apparent from thedetailed specification, and thus, it is intended that the appendedclaims cover all systems and methods falling within the true spirit andscope of the disclosure. As used herein, the indefinite articles “a” and“an” mean “one or more.” Similarly, the use of a plural term does notnecessarily denote a plurality unless it is unambiguous in the givencontext. Words such as “and” or “or” mean “and/or” unless specificallydirected otherwise. Further, since numerous modifications and variationswill readily occur from studying the present disclosure, it is notdesired to limit the disclosure to the exact construction and operationillustrated and described, and accordingly, all suitable modificationsand equivalents may be resorted to, falling within the scope of thedisclosure.

Other embodiments will be apparent from consideration of thespecification and practice of the embodiments disclosed herein. It isintended that the specification and examples be considered as exampleonly, with a true scope and spirit of the disclosed embodiments beingindicated by the following claims.

According to some embodiments, the operations, techniques, and/orcomponents described herein can be implemented by a device or system,which can include one or more special-purpose computing devices. Thespecial-purpose computing devices can be hard-wired to perform theoperations, techniques, and/or components described herein, or caninclude digital electronic devices such as one or moreapplication-specific integrated circuits (ASICs) or field programmablegate arrays (FPGAs) that are persistently programmed to perform theoperations, techniques and/or components described herein, or caninclude one or more hardware processors programmed to perform suchfeatures of the present disclosure pursuant to program instructions infirmware, memory, other storage, or a combination. Such special-purposecomputing devices can also combine custom hard-wired logic, ASICs, orFPGAs with custom programming to accomplish the technique and otherfeatures of the present disclosure. The special-purpose computingdevices can be desktop computer systems, portable computer systems,handheld devices, networking devices, or any other device that canincorporate hard-wired and/or program logic to implement the techniquesand other features of the present disclosure.

The one or more special-purpose computing devices can be generallycontrolled and coordinated by operating system software, such as iOS,Android, Blackberry, Chrome OS, Windows XP, Windows Vista, Windows 7,Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris,VxWorks, or other compatible operating systems. In other embodiments,the computing device can be controlled by a proprietary operatingsystem. Operating systems can control and schedule computer processesfor execution, perform memory management, provide file system,networking, I/O services, and provide a user interface functionality,such as a graphical user interface (“GUI”), among other things.

Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above described examples, but instead are defined by theappended claims in light of their full scope of equivalents.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps.

It is intended, therefore, that the specification and examples beconsidered as example only, with a true scope and spirit being indicatedby the following claims and their full scope of equivalents.

1-29. (canceled)
 30. A system comprising: a central data locationconfigured to collect information, the central data location comprising:an event backbone configured to receive transactional event data, theevent backbone comprising: a data scheme topic; and a common data schemetopic formed from the data scheme topic; and an ingestion connectorcommunicatively connected to the event backbone, the ingestion connectorconfigured to: receive, from a system of record, a transactional event;and extract the transactional event data from the transactional event,the ingestion connector comprising a change data capture configured todetermine data changes in the system of record when the transactionalevent occurs; and place the transactional event data onto the datascheme topic when the transactional event occurs such that the commondata scheme topic is formed with the transactional event data.
 31. Thesystem of claim 30, wherein the central data location further comprisesa streaming processor configured to stream the transactional event datato a subscriber.
 32. The system of claim 30, wherein the change datacapture determines the transactional event data is changed.
 33. Thesystem of claim 30, wherein the ingestion connector further comprises amessage-oriented middleware component configured to receive thetransactional event data from the change data capture and send thetransactional event data to the event backbone.
 34. The system of claim30, wherein the ingestion connector further comprises a connecting logiccommunicatively connected to the change data capture, the connectinglogic configured to connect the ingestion connector to the eventbackbone.
 35. The system of claim 30, wherein the central data locationis configured to: determine whether the system of record and the eventbackbone comprise the transactional event data; and determine whetherthe transactional event is a new event not yet placed onto the datascheme topic when the system of record comprises the transactional eventdata and the event backbone does not comprise the transactional eventdata.
 36. The system of claim 30, wherein the central data locationfurther comprises an event store communicatively connected to the eventbackbone, the event store being configured to: receive the common datascheme topic from the event backbone; and store the common data schemetopic in a storage system.
 37. The system of claim 36, wherein the eventstore further comprises a database.
 38. The system of claim 37, whereinthe database is a RDBMS database.
 39. The system of claim 37, whereinthe database is a NoSQL database.
 40. The system of claim 30, whereinthe common data scheme topic is a BIAN topic.
 41. The system of claim30, wherein: the central data location further comprises a logmanagement system; and the event backbone further comprises an accesslogs topic communicatively coupled to the log management system, the logmanagement system configured to record access to the event backbone. 42.A system comprising: a central data location configured to collectinformation, the central data location comprising: an event backboneconfigured to receive transactional event data, the event backbonecomprising: a data scheme topic; and a common data scheme topic formedfrom the data scheme topic; and an ingestion connector configured toreceive, from a system of record, a batch file comprising thetransactional event data, the ingestion connector comprising a batchfile processor configured to, in response to an event, place thetransactional event data onto the data scheme topic such that the commondata scheme topic, being formed from the data scheme topic, is formedwith the transactional event data.
 43. The system of claim 42,comprising a streaming processor configured to stream, to a subscriber,a data scheme message.
 44. The system of claim 42, wherein the centraldata location is configured to: determine whether the system of recordand the event backbone comprise the transactional event data; anddetermine whether the transactional event is a new event not yet placedonto the data scheme topic when the system of record comprises thetransactional event data and the event backbone does not comprise thetransactional event data.
 45. The system of claim 42, wherein thecentral data location comprises an event store configured to store thecommon data scheme topic.
 46. The system of claim 45, wherein the eventstore further comprises a database.
 47. The system of claim 46, whereinthe database is a RDBMS database.
 48. The system of claim 46, whereinthe database is a NoSQL database.
 49. The system of claim 42, whereinthe event is an end-of-day reconciliation.